Skip to content

feat(framework): sync the system prompt with the #326 doc (#555)#557

Merged
suleimansh merged 1 commit into
mainfrom
feat/sync-system-prompt-555
Jul 15, 2026
Merged

feat(framework): sync the system prompt with the #326 doc (#555)#557
suleimansh merged 1 commit into
mainfrom
feat/sync-system-prompt-555

Conversation

@suleimansh

Copy link
Copy Markdown
Member

Closes #555

The shipped system prompt was the 11-Jul draft. The #326 doc was rewritten on 13-Jul and never synced, so every run since has been driven by a stale prompt. prompts/system_prompt.md is byte-identical to the OP first ```md block again, verified by comparing the built constant against the block fetched from the API rather than by hand-copying.

The prompt diff is the review. What the agent gets that it did not before:

  • ## Analyze the user prompt, and the ANLYSIS_RESULT.md + ADD_ANALYSIS_ENTRY flow.
  • ## Before starting changes -> ### Session name: commit a dirty tree, create and check out the-framework/<SESSION_NAME>, call setSessionName(). This one never shipped at all. It reached the agent only as an aside inside the signal protocol, so the paraphrase shipped and the doc did not.
  • ## After applying changes: call setReadyForMerge() when the session has no work left.
  • Renames: ## Unclear scope -> ### Ambiguous prompt, ## Large scope -> ### Scope, ## Alternatives moves under ## Before applying changes.
  • ## Maintenance leaves this block. It moves to the post-merge prompt, which is Post-merge prompt: add TODO entries instead of running the presets inline #556.

showMarkdownSecondary() emits the same show-markdown block as showMarkdown(), per the OP note that for the MVP the two can be equivalent.

The sync silently breaks the eco flags, so they are fixed here. ECO_SECTION_HEADINGS drops sections by exact heading string (## Large scope, ## Alternatives, ## Maintenance) and the rewrite renames or moves all three. dropSection() no-ops on a missing heading, so --eco-auto-planning and --eco-auto-research would have stopped trimming anything with zero test failures: the eco tests assert !system.includes("## Large scope"), which passes for free once that heading is gone. Fixed by retargeting them at ### Scope / ### Alternatives, making dropSection() level-aware so dropping a ### stops at its sibling instead of swallowing the next ##, and asserting the drop actually shortens the prompt. Reverting one heading to its old string now fails 3 tests with "eco.autoPlanning dropped nothing"; before it failed none.

--eco-auto-maintenance is inert after this: its section left the system prompt, so there is nothing here to trim and the tokens are already saved for every run. The flag stays parsed and persisted and re-points at the post-merge prompt in #556.

Measured, extracted from the built values rather than inferred:

constant before after
SYSTEM_PROMPT 1964 2354
PROTOCOLS_AWAIT 1415 1527
composeRunSystem 3874 4475

Every preset constant is untouched. 522 pass, 0 fail, typecheck green across all 21 packages.

The shipped prompt was the 11-Jul draft. The #326 doc was rewritten on
13-Jul and never synced, so every run since has been driven by a stale
prompt. prompts/system_prompt.md is byte-identical to the doc again.

Also retarget the eco flags, which the sync breaks silently: they drop
sections by exact heading string and the rewrite renames or moves all
three, and a missing heading is a no-op.
@suleimansh suleimansh added bug Something isn't working priority: high Should be addressed soon the-framework ♻️ labels Jul 15, 2026
@suleimansh suleimansh self-assigned this Jul 15, 2026
@suleimansh suleimansh merged commit 2fc612a into main Jul 15, 2026
2 checks passed
@suleimansh suleimansh deleted the feat/sync-system-prompt-555 branch July 15, 2026 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working priority: high Should be addressed soon the-framework ♻️

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sync the system prompt with the #326 doc

1 participant